Sourced from com.google.dagger:hilt-android's releases.

Dagger 2.50

Dagger

Potential breaking changes

• Introduced a new dagger.internal.Provider to facilitate future support for jakarta.inject.Provider types. There should be no visible changes at this time, though with such a large change there is a risk of unanticipated version compatibility issues across libraries built with different Dagger versions. (75d3cbcf9)
• Flip the default for -Adagger.explicitBindingConflictsWithInject to enabled. This flag fixes a bug where an explicit binding like an @Provides should conflict with @Inject bindings if the @Inject is actually used in a parent component. (8372c6308)

Bug fixes

• Fixed the error message for an @Binds @IntoSet implementation with duplicate bindings. (8d0122322)

Dagger 2.49

Dagger

New features:

• Fixed #4044: Add support for KSP with dagger.android (832717767).

Potential breaking changes:

• Dagger’s generated component no longer contains deprecated no-op module setter methods for modules that have only static/abstract @Provides/@Binds methods (ed47d4b88).

  Note: If you hit this issue, the fix is to remove the call to the setter method in your code. For example:

  MyComponent component =
      DaggerMyComponent.builder()
  -        .moduleWithOnlyStaticOrAbstractMethods(new ModuleWithOnlyStaticOrAbstractMethods())
          .build();

  These setter methods were already no-ops (i.e. Dagger just ignored them), so removing it should not cause any functional changes.

Bug fixes:

• Fixed #4046, #4140: Fixes Unexpected element error in when calculating nullability (4593c0a)
• Fixed #4096: Fix type names for inline types on the KSP side (aosp/2789273)
• Build-time performance improvements (85e9ff1) and (d9d0a8e).
• Fixed #4060: Updated KSP to 1.9.20-1.0.14 which should contain the fix for a number of incremental processing issues related to KSP (692015f).

Hilt

New features:

• Fixed google/dagger#2287, #3523: Add support for using @AssistedInject with @HiltViewModel. (8327177). For more details visit https://dagger.dev/hilt/view-model#assisted-injection.
• Hilt now provides @ActivityRetainedSavedState SavedStateHandle from ActivityRetainedComponent (1cac33b). Note: This feature relies on a somewhat experimental implementation in order to provide this binding lazily while also avoiding leaking the activity. The laziness is a requirement to not restrict activity injection and also to avoid bloating the saved state when unused. While we predict this should be safe to rely on, if issues are discovered with this implementation, it is possible that a future release may have to remove this binding.

Bug fixes:

... (truncated)

• 137995b 2.50 release
• 8d01223 Fix error message for an @Binds @IntoSet implementation with duplicate bind...
• be77d24 Dagger build performance optimizations.
• 8372c63 Flip the default for explicitBindingConflictsWithInject to enabled.
• 13d64c6 Internal changes
• 5f8b76c Optimize InjectionSiteFactory#getInjectionSites().
• 45af1ed Increase timeout for emulator tests from 25min to 35min in CI.
• 45d3b87 Make minSdk and targetSdk versions consistent across Gradle tests.
• f4b4519 Internal changes
• eb9a034 Configure Bazel and Gradle to avoid spurious flakes.
• Additional commits viewable in compare view

Sourced from com.google.dagger:hilt-android-compiler's releases.

Dagger 2.50

Dagger

Potential breaking changes

• Introduced a new dagger.internal.Provider to facilitate future support for jakarta.inject.Provider types. There should be no visible changes at this time, though with such a large change there is a risk of unanticipated version compatibility issues across libraries built with different Dagger versions. (75d3cbcf9)
• Flip the default for -Adagger.explicitBindingConflictsWithInject to enabled. This flag fixes a bug where an explicit binding like an @Provides should conflict with @Inject bindings if the @Inject is actually used in a parent component. (8372c6308)

Bug fixes

• Fixed the error message for an @Binds @IntoSet implementation with duplicate bindings. (8d0122322)

Dagger 2.49

Dagger

New features:

• Fixed #4044: Add support for KSP with dagger.android (832717767).

Potential breaking changes:

• Dagger’s generated component no longer contains deprecated no-op module setter methods for modules that have only static/abstract @Provides/@Binds methods (ed47d4b88).

  Note: If you hit this issue, the fix is to remove the call to the setter method in your code. For example:

  MyComponent component =
      DaggerMyComponent.builder()
  -        .moduleWithOnlyStaticOrAbstractMethods(new ModuleWithOnlyStaticOrAbstractMethods())
          .build();

  These setter methods were already no-ops (i.e. Dagger just ignored them), so removing it should not cause any functional changes.

Bug fixes:

• Fixed #4046, #4140: Fixes Unexpected element error in when calculating nullability (4593c0a)
• Fixed #4096: Fix type names for inline types on the KSP side (aosp/2789273)
• Build-time performance improvements (85e9ff1) and (d9d0a8e).
• Fixed #4060: Updated KSP to 1.9.20-1.0.14 which should contain the fix for a number of incremental processing issues related to KSP (692015f).

Hilt

New features:

• Fixed google/dagger#2287, #3523: Add support for using @AssistedInject with @HiltViewModel. (8327177). For more details visit https://dagger.dev/hilt/view-model#assisted-injection.
• Hilt now provides @ActivityRetainedSavedState SavedStateHandle from ActivityRetainedComponent (1cac33b). Note: This feature relies on a somewhat experimental implementation in order to provide this binding lazily while also avoiding leaking the activity. The laziness is a requirement to not restrict activity injection and also to avoid bloating the saved state when unused. While we predict this should be safe to rely on, if issues are discovered with this implementation, it is possible that a future release may have to remove this binding.

Bug fixes:

... (truncated)

• 137995b 2.50 release
• 8d01223 Fix error message for an @Binds @IntoSet implementation with duplicate bind...
• be77d24 Dagger build performance optimizations.
• 8372c63 Flip the default for explicitBindingConflictsWithInject to enabled.
• 13d64c6 Internal changes
• 5f8b76c Optimize InjectionSiteFactory#getInjectionSites().
• 45af1ed Increase timeout for emulator tests from 25min to 35min in CI.
• 45d3b87 Make minSdk and targetSdk versions consistent across Gradle tests.
• f4b4519 Internal changes
• eb9a034 Configure Bazel and Gradle to avoid spurious flakes.
• Additional commits viewable in compare view

Sourced from com.google.dagger:hilt-android-testing's releases.

Dagger 2.50

Dagger

Potential breaking changes

• Introduced a new dagger.internal.Provider to facilitate future support for jakarta.inject.Provider types. There should be no visible changes at this time, though with such a large change there is a risk of unanticipated version compatibility issues across libraries built with different Dagger versions. (75d3cbcf9)
• Flip the default for -Adagger.explicitBindingConflictsWithInject to enabled. This flag fixes a bug where an explicit binding like an @Provides should conflict with @Inject bindings if the @Inject is actually used in a parent component. (8372c6308)

Bug fixes

• Fixed the error message for an @Binds @IntoSet implementation with duplicate bindings. (8d0122322)

Dagger 2.49

Dagger

New features:

• Fixed #4044: Add support for KSP with dagger.android (832717767).

Potential breaking changes:

• Dagger’s generated component no longer contains deprecated no-op module setter methods for modules that have only static/abstract @Provides/@Binds methods (ed47d4b88).

  Note: If you hit this issue, the fix is to remove the call to the setter method in your code. For example:

  MyComponent component =
      DaggerMyComponent.builder()
  -        .moduleWithOnlyStaticOrAbstractMethods(new ModuleWithOnlyStaticOrAbstractMethods())
          .build();

  These setter methods were already no-ops (i.e. Dagger just ignored them), so removing it should not cause any functional changes.

Bug fixes:

• Fixed #4046, #4140: Fixes Unexpected element error in when calculating nullability (4593c0a)
• Fixed #4096: Fix type names for inline types on the KSP side (aosp/2789273)
• Build-time performance improvements (85e9ff1) and (d9d0a8e).
• Fixed #4060: Updated KSP to 1.9.20-1.0.14 which should contain the fix for a number of incremental processing issues related to KSP (692015f).

Hilt

New features:

• Fixed google/dagger#2287, #3523: Add support for using @AssistedInject with @HiltViewModel. (8327177). For more details visit https://dagger.dev/hilt/view-model#assisted-injection.
• Hilt now provides @ActivityRetainedSavedState SavedStateHandle from ActivityRetainedComponent (1cac33b). Note: This feature relies on a somewhat experimental implementation in order to provide this binding lazily while also avoiding leaking the activity. The laziness is a requirement to not restrict activity injection and also to avoid bloating the saved state when unused. While we predict this should be safe to rely on, if issues are discovered with this implementation, it is possible that a future release may have to remove this binding.

Bug fixes:

... (truncated)

• 137995b 2.50 release
• 8d01223 Fix error message for an @Binds @IntoSet implementation with duplicate bind...
• be77d24 Dagger build performance optimizations.
• 8372c63 Flip the default for explicitBindingConflictsWithInject to enabled.
• 13d64c6 Internal changes
• 5f8b76c Optimize InjectionSiteFactory#getInjectionSites().
• 45af1ed Increase timeout for emulator tests from 25min to 35min in CI.
• 45d3b87 Make minSdk and targetSdk versions consistent across Gradle tests.
• f4b4519 Internal changes
• eb9a034 Configure Bazel and Gradle to avoid spurious flakes.
• Additional commits viewable in compare view

Sourced from com.google.dagger.hilt.android's releases.

Dagger 2.50

Dagger

Potential breaking changes

• Introduced a new dagger.internal.Provider to facilitate future support for jakarta.inject.Provider types. There should be no visible changes at this time, though with such a large change there is a risk of unanticipated version compatibility issues across libraries built with different Dagger versions. (75d3cbcf9)
• Flip the default for -Adagger.explicitBindingConflictsWithInject to enabled. This flag fixes a bug where an explicit binding like an @Provides should conflict with @Inject bindings if the @Inject is actually used in a parent component. (8372c6308)

Bug fixes

• Fixed the error message for an @Binds @IntoSet implementation with duplicate bindings. (8d0122322)

Dagger 2.49

Dagger

New features:

• Fixed #4044: Add support for KSP with dagger.android (832717767).

Potential breaking changes:

• Dagger’s generated component no longer contains deprecated no-op module setter methods for modules that have only static/abstract @Provides/@Binds methods (ed47d4b88).

  Note: If you hit this issue, the fix is to remove the call to the setter method in your code. For example:

  MyComponent component =
      DaggerMyComponent.builder()
  -        .moduleWithOnlyStaticOrAbstractMethods(new ModuleWithOnlyStaticOrAbstractMethods())
          .build();

  These setter methods were already no-ops (i.e. Dagger just ignored them), so removing it should not cause any functional changes.

Bug fixes:

• Fixed #4046, #4140: Fixes Unexpected element error in when calculating nullability (4593c0a)
• Fixed #4096: Fix type names for inline types on the KSP side (aosp/2789273)
• Build-time performance improvements (85e9ff1) and (d9d0a8e).
• Fixed #4060: Updated KSP to 1.9.20-1.0.14 which should contain the fix for a number of incremental processing issues related to KSP (692015f).

Hilt

New features:

• Fixed google/dagger#2287, #3523: Add support for using @AssistedInject with @HiltViewModel. (8327177). For more details visit https://dagger.dev/hilt/view-model#assisted-injection.
• Hilt now provides @ActivityRetainedSavedState SavedStateHandle from ActivityRetainedComponent (1cac33b). Note: This feature relies on a somewhat experimental implementation in order to provide this binding lazily while also avoiding leaking the activity. The laziness is a requirement to not restrict activity injection and also to avoid bloating the saved state when unused. While we predict this should be safe to rely on, if issues are discovered with this implementation, it is possible that a future release may have to remove this binding.

Bug fixes:

... (truncated)

• 137995b 2.50 release
• 8d01223 Fix error message for an @Binds @IntoSet implementation with duplicate bind...
• be77d24 Dagger build performance optimizations.
• 8372c63 Flip the default for explicitBindingConflictsWithInject to enabled.
• 13d64c6 Internal changes
• 5f8b76c Optimize InjectionSiteFactory#getInjectionSites().
• 45af1ed Increase timeout for emulator tests from 25min to 35min in CI.
• 45d3b87 Make minSdk and targetSdk versions consistent across Gradle tests.
• f4b4519 Internal changes
• eb9a034 Configure Bazel and Gradle to avoid spurious flakes.
• Additional commits viewable in compare view

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)